Universal system for enabling dynamically discounted buyer-vendor payments

ABSTRACT

Methods, systems and instructions stored on computer-readable media for receiving a plurality of invoices associated a vendor and one or more buyers. Each invoice is associated with a respective buyer and includes an invoice amount to be paid by a deadline. Each invoice is sent to the respective buyer. Possible early payment invoices that are available for early payment prior to the respective deadline from the plurality of invoices are determined. Notification, including a discount, is sent to the vendor regarding the possible early payment invoices. Approval to receive early payment of one or more of the possible early payment invoices is determined. A vendor financial institution and account, and buyer financial institutions and accounts are determined. A quantity of funds based upon the invoice amount and the discount of the one or more of the possible early payment invoices is transferred from the buyer accounts to the vendor account.

BACKGROUND

The following description is provided to assist the understanding of thereader. None of the information provided or references cited is admittedto be prior art.

In the normal course of business, a company can utilize a number ofvendors to procure needed products and services. As a company can beboth a buyer and a vendor, a buyer refers to a company that ispurchasing goods or services, and a vendor is a company that sells goodsor services. FIG. 1 is a graph 100 of a common relationship between abuyer's amount of purchases and the number of vendors used by the buyer.Some buyers spend a large amount at a small number of vendors (102).These buyers though tend to still have numerous vendors that providesmaller amounts of products and services (104).

In instances where the buyer is a very large corporation, with verysubstantial financial resources, and the vendors that represent themajority of purchases are also very large corporations, with verysubstantial financial resources, costly, complex and customizedelectronic supply chain order, fulfillment, invoice presentment andpayment systems are sometimes implemented. Once these complex systemshave been implemented, the large buyer and vendor are able to interactwith one another in a nearly paperless fashion, including purchase orderdelivery, invoicing and payment. These systems are often referred to asclosed loop environments, as the platforms are not extendable, withoutdeep and costly integration, to all other customers or vendors. Often,these systems rely on electronic data interchange (EDI) interfaces,provided by third parties, to deliver data to one another. And, whenpayment is due, these systems rely on integrations with bank softwareplatforms to deliver electronic payment via the Automated Clearing House(ACH). The deep customized integration that can exist in these highlycomplex and costly systems, by its very nature, requires substantialeffort, often completed by third party consultants, to design andimplement. And, once the system is designed, both buyer and vendor muststill allocate substantial management and staff resources during thesetup process. All of the above ignores completely that finding vendorsand buyers, completing and responding to requests for proposals (RFPs),and “setting up vendors and customers” within each other's accounting orenterprise resource planning systems is time consuming, manual andrelies heavily on the acquisition of information that can only beprovided directly by the counter party. That said, once the system iscomplete, efficiencies still improve. In other circumstances such deepintegration is simply not practical. For instance, in the retail sector,consumer tastes change so rapidly that many purchases from vendors mustbe managed on a moment-by-moment basis. Notwithstanding, large buyerswith substantial financial resources still work very hard to eke out asmuch efficiency from the procurement process as possible, often at theexpense of their much smaller vendors, who are forced to comply with thevariant invoicing requirements and standards imposed upon them by theirlarge customers. And even then these systems are generally designed forvendors that supply valuable inventory, and are not implemented withsmall infrequently used vendors supplying items that would generally beclassified as general and administrative expense items.

In many cases, these large buyers eschew deep integration and simplyrequire their vendors to communicate with them concerning transactionalinformation via Electronic Data Interchange. In these cases, the vendoris generally required to hire a third party integrator to serve as anintermediary to enable them to receive each of their customers'electronic orders and comply with each of their customers' uniqueinvoicing requirements. The introduction of a third party integrator isan expensive necessity for vendors who choose to do business with thesecustomers. It should be noted that it is highly unusual that all of avendor's customers require EDI integration, and as a result, vendors arerequired to maintain many disparate processes to support and managetheir many customer relationships. Some customers receive invoices viaEDI, some via paper, others via email. Managing the funds owed by theircustomers is equally inefficient for small and large vendors alike.

In rare circumstances, large buyers with substantial financial resourceshave gone to the trouble and expense of developing, or purchasing,Electronic Invoice Presentment and Payment (“EIPP”) solutions tocommunicate invoice and payment status to vendors. However, this remainsrare, and even where it exists, the invoice and payment information isbuyer specific. That is to say, when vendors sell to buyers that have aplatform that provides invoice and payment information, each system isunique and independent, a closed loop. And even then, there is nostandardization within these platforms (the information available isdifferent, both in terms of its type, presentation, access, etc.), andas a result, even in the rare circumstances where an online system isavailable, the acquisition of invoice and payment status acrosscustomers is time consuming and inefficient. In most cases, no data isavailable online and vendors must call each of their customers on thephone, or email them, to obtain invoice and payment information,necessitating customer response to these calls and emails.

All of the above consume substantial time and effort for both the buyerand vendor.

Electronic invoice and presentment solutions are generally designed tomeaningfully improve the efficiency of a large buyer with a large numberof disparate vendors. This improvement is accomplished in numerous ways,but heavily focuses on the elimination of paper handling, data entry,and manual invoice approval among accounts payable departments. Thesolutions are, by design, buyer-centric. The buyer receives increasedefficiency at the expense of the vendor, who must comply with specificinvoice requirements mandated by the buyer. This arrangement often meansthat the vendor must submit invoices to the buyer following very precisebusiness rules that often force vendors to ignore the invoice printingand email functions that exist within their accounting softwareplatforms, instead submitting invoice information to various customersusing unique buyer-specific one off processes. While electronic invoicepresentment and payment systems can integrate into a buyer's accountingsystem, they rarely integrate with similar efficiency into the systemsof their vendors, and then, only within custom designed and highlycomplex systems available only to the largest vendors with substantialfinancial resources. Even then, the integration is unique to thespecific buyer-vendor relationship, rather than to all buyers, andconversely, all vendors. In the rare cases where a customer has made anonline invoice status system uniquely available to the vendor, if avendor needed to request the modification of an invoice after deliveryto their buyer, the vendor would need to make the change within theirown accounting system, and then resubmit the corrected invoice, orcredit memo, to their customer, in a duplicative process.

Smaller vendors with fewer financial resources, or that sell smallquantities of goods or services, particularly on an infrequent basis, orlarger vendors with substantial financial resources that sell a smallamount of product to their customers, simply have too little capital,sophistication, or financial incentive to undertake such integrationprojects or implement an EDI relationship. In these circumstances,relationships generally involve the production and mailing of a largenumber of paper invoices, manual buyer approvals, data entry, collectionphone calls and, ultimately, payments by check.

SUMMARY

In general, one aspect of the subject matter described in thisspecification can be embodied in methods for receiving a plurality ofinvoices associated a vendor and one or more buyers. Each invoice isassociated with a respective buyer and includes an invoice amount to bepaid by a deadline. Each invoice is sent to the respective buyer.Possible early payment invoices that are available for early paymentprior to the respective deadline from the plurality of invoices aredetermined. Notification is sent to the vendor regarding the possibleearly payment invoices. Each notification includes a respective discountof the invoice. Approval to receive early payment of one or more of thepossible early payment invoices is determined. A vendor financialinstitution and a vendor account associated with the vendor and buyerfinancial institutions and buyer accounts associated with the one ormore buyers are determined. The vendor is not required to know the buyerfinancial institutions and the buyer accounts. A quantity of funds istransferred from the buyer accounts at the buyer financial institutionsto the vendor account at the vendor financial institution. The quantityof funds is based upon the invoice amount in view of the respectivediscount of the one or more of the possible early payment invoices.Other implementations of this aspect include corresponding systems,apparatuses, and computer-readable media configured to perform theactions of the method.

BRIEF DESCRIPTION OF THE DRAWINGS

The details of one or more implementations of the subject matterdescribed in this specification are set forth in the accompanyingdrawings and the description below. Other features, aspects, andadvantages of the subject matter will become apparent from thedescription, the drawings, and the claims.

FIG. 1 is a graph of a common relationship between a buyer's amount ofpurchases and the number of vendors used by the buyer.

FIG. 2 is a block diagram of an accounting system in accordance with anillustrative implementation.

FIG. 3 is a timing diagram of paying an invoice using a universalpayment module in accordance with an illustrative implementation.

FIG. 4 is a timing diagram of a change request using a universal paymentmodule in accordance with an illustrative implementation.

FIGS. 5A-5B are timing diagrams of requesting early payment of aninvoice in accordance with an illustrative implementation.

FIG. 6 illustrates a listing of invoices that are available for earlypayment in accordance with an illustrative implementation.

FIG. 7 illustrates an ordered list of invoices for early payment inaccordance with an illustrative implementation.

FIG. 8 illustrates a discount graph in accordance with an illustrativeimplementation.

FIG. 9 is a block diagram of a computer system in accordance with anillustrative implementation.

FIGS. 10-16 are screenshots of a user interface in accordance with anillustrative implementation.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

A system utilizing a universal payment module (UPM) can extend thebenefits of a specialized electronic invoicing system to all vendors,and all buyers, regardless of size or accounting system used by thevendor. FIG. 2 is a block diagram of an accounting system in accordancewith an illustrative implementation of such a system. A vendor 202 and abuyer 206 can interact with one another using a universal payment module(UPM) 204. As a vendor is a business entity that likely purchasesproducts and services, a vendor can also be a buyer and vice versa. TheUPM 204 is configured to interface with the accounting system of thevendor 202 and also the accounting system of the buyer 206. In addition,the UPM 204 can facilitate the deposit of funds into the accounts of thevendor 202 and/or the buyer 206 at financial institutions. In oneimplementation, the buyer 206 can authorize payment of a vendor'sinvoice using the UPM 204. Based on the payment authorization, the UPM204 can provide information regarding an invoice to a customer. In oneimplementation, an indication of the financial institution and accountassociated with the buyer can be provided to the buyer. In anotherimplementation, a buyer's default financial institution and account canbe used and no indication needs to be provided to the buyer. Thecustomer can then create a check based upon this data and send the checkto the UPM 204. This check creation is preferably done electronically.After receiving the check via an electronic communication, the UPM 204can facilitate the deposit of funds into the appropriate vendor'saccount in numerous ways. In one implementation, the UPM 204 can printthe check on behalf of the buyer. The printed check can be sent to thevendor or be used to create an image cash letter (ICL) for transmissionto the vendor's financial institution. The ICL can be created to complywith various laws and regulations, e.g., Check 21, UCC, etc. Regardlessof whether the check is printed, the UPM 204 can facilitate the depositof the check into a vendor's account. Typically, a deposit via ICLrequires financial institutions to set up ICL services for each account.The setup procedure can require credit approval, technologicalsophistication, equipment such as scanners, test file submission andconfirmation, substantial legal documentation, etc. Traditionally, theaccount set-up process is entirely manual, can take several weeks postapproval, and costs thousands of dollars. This process can be long andpainful and can require technology integration with numerous test filesand confirmations flowing back and forth to confirm data integrity andconsistency. Accordingly, it is in neither the financial institution'sor small customer's interest to deposit payments via ICL, and yet,depositing funds at financial institution branch locations remainsexceedingly inefficient for both financial institution customers and forfinancial institutions. A system using the UPM 204 can resolve theseissues. Financial institutions that interface with a system using theUPM 204 can authorize the UPM to submit ICL files which aggregatedeposits in separate or comingled image cash letters within the ICLfile, for the benefit of their customers. In addition, as necessary,vendors connected to a UPM-enabled system may also delegate authority tothe system. A system with the UPM, thus, serves as an aggregator ofpayments for connected vendors. In so doing, the UPM-enabled systemcreates tremendous efficiency for the financial institution and for thevendors, as the financial institution may now enable the electronicdeposit for all its customers without having to set up any of itscustomers for ICL deposit services. Rather, it approves and confirms theUPM-enabled system's ability to submit acceptable ICL files, and toremain compliant with a financial institution's requirements, andthrough the UPM, all customers can now enable electronic deposit.

Vendors can opt into ICL deposits through the UPM 204. If a vendor hasopted into ICL deposits through the UPM 204, the UPM 204 canelectronically initiate the deposit of the buyer's check payment intothe vendor's account. In this example, the buyer is not required to knowany of the vendor's financial account information, and therefore, theUPM 204 does not make this information available to the buyer. The UPM204, however, knows the vendor's financial account information and canuse this information to initiate the deposit. Accordingly, the vendor'sfinancial account information is protected from the buyer's visibility.This arrangement is unlike solutions that rely solely on ACH payments.In ACH systems, buyers seek to obtain the bank account information oftheir vendors, and then buyers set up, through a cumbersome and tediousmanual process, ACH payment capabilities within their financialinstitution's systems. Further, to the extent they want to make paymentsfrom accounts at multiple financial institutions, the same manual set upprocess must be duplicated. Unfortunately, there can be little trustamong companies, hampering the acquisition by buyers of their vendors'bank account information. Further, small vendors are often thinlystaffed, and the very act of a buyer getting an authorizedrepresentative of the vendor on the phone to acquire bank accountinformation can be tedious and expensive, and is often unsuccessful. Asystem using the UPM 204 can help address this issue of ACH systems,since the account information of the buyer and vendor are not shared. Asdescribed in greater detail below, buyers and vendors can provide theiraccount information one time to the a UPM-enabled system. Further, it isnot necessary for the UPM-enabled system to share the accountinformation of one user with another user to further payment of aninvoice. The UPM-enabled system can, therefore, protect the accountinformation from being distributed to parties that do not require theaccount information, while still facilitating payment with seamlessefficiency from one user to another. As explained in greater detailbelow, the UPM-enabled system allows buyers and vendors to interact invarious other ways. Before using the UPM-enabled system, a company mustfirst register with the system.

Registration

A company can join the UPM-enabled system in a number of ways. Forexample, a previously-registered company can request that its buyersand/or vendors register with the UPM-enabled system. Using the vendorand buyer data present in the UPM-enabled system, an email containing aninvitation to register can be sent to each company or a subset ofcompanies associated with the registered company. This registration caninclude tokenized information within the invitation so that theregistration link can identify the connection between the two companiesas registration occurs, and after registration the invited company canhave immediate visibility to the inviting company. Further, as to theregistration process, since the UPM-enabled system includes connectionsto a network of companies, the UPM-enabled system is aware of the myriadrelationships that can exist within and among companies and can identifycircumstances, and invite companies to register, where benefit islikely. For instance, if multiple vendors connected to the UPM-enabledsystem all sell to the same customer, but the customer is not yet on theUPM-enabled system, the system can make the customer aware of theconnections that already are known, the benefits that can existimmediately upon connection, and suggest a connection even incircumstances where the customer would not be aware of the existingconnections, and thus benefits.

In one implementation, once a connection request is received, a companycan begin the UPM registration process. As a previously registeredcompany invited the company, the UPM-enabled system has data related tothe invited company. This data can be used during the registrationprocess to avoid duplicative data entry. For example, if the invitingcompany is already in possession of the address, phone number, faxnumber, doing-business-as name, etc. from having previously sold to theinvitee, or the data was simply in its accounting software and was“synced” to the UPM-enabled system, the same data can be pre-populatedwithin the registration page, limiting the amount of additional data theinvitee must enter to register. The invitee has, of course, the abilityto correct any incorrect data provided by the inviting company.Alternatively, an uninvited company can register with the UPM-enabledsystem.

After registering, a company can log into the UPM-enabled system and seeany available invoice information from the inviting company. Forexample, in the instance where the invited company was a vendor of thecompany that initiated the invitation, upon registration it would beable to see the open invoices associated with the inviting company, andthe invoice status thereof. In addition, once the company's data hasbeen synchronized with the UPM-enabled system, the invited company caninvite its own vendors and buyers.

In traditional systems, before a buyer can pay a vendor, or in somecases do business with a new vendor, the vendor must be “set up” in thebuyer's accounting and/or ERP system. This process is generally manualand must be completed with each new relationship that either the vendoror buyer develops. Further, when any captured information changes in thefuture, it is incumbent on the vendor, or buyer, to notify all of theiractive (or inactive) vendors or buyers, of the change, a manual andinefficient process. This information can include W-9 forms andelectronic payment information, enabling buyers to make electronicpayment to vendors using conventional ACH functionality. In contrast,the UPM-enabled system, acting in its capacity as a network, allows anyvendor to complete their typical set-up information once and storerelevant information on the UPM. In so doing, all new customersconnecting with the vendor over the UPM-enabled system can access andintegrate all needed information within their accounting or ERP systemsat the click of a button. Accounts payable and accounts receivabledepartments can use the UPM-enabled system to set up new vendors andcustomers, as the UPM-enabled system serves as the central repositoryfor such information, across all companies. Further, any updates to thisinformation can notify the vendor/buyer counterparties of the changes,allowing anyone to distribute updated information at the click of abutton. The above is particularly important with infrequently usedvendors, where the cost of set-up, in comparison to the amount ofpurchases, is particularly high. There remains a significant lack oftrust between buyers and vendors, particularly as it relates toelectronic payment information and small vendors. As a result, the UPM,can serve to safeguard the delivery of certain information, while notimpeding the functionality or efficiency of relationships. For instance,the UPM can serve as the central repository for counterparty accountinformation. In this capacity, the UPM-enabled system, through itspayment capabilities (described in greater detail below) can associatethe payment information with the counterparty without ever sharing theinformation, enabling buyers to make payment directly to the accounts ofvendors without ever being provided vendor payment information.

Once registered, a company can also set up accounts. For example, acompany can provide account information of one or more company accounts,e.g., bank accounts. These accounts can be used to make and/or receivepayments. As explained in greater detail below, a buyer can pay aninvoice from anywhere, at any time, on any device connected to theinternet, whether by check or otherwise. Further, a vendor can receivethe payment into any set-up account associated with the vendor, all bysharing payment information with the UPM-enabled system once rather thanwith each buyer, who would then come into possession of confidentialaccount information. Accordingly, the UPM-enabled system can become acentral repository of data and as described in greater detail below,allow parties to make payments without having to share paymentinformation with other parties. In addition, as described in greaterdetail below, the UPM-enabled system can convert accounting data into acommon form, which allows the UPM-enabled system to become astandardized source of information and facilitates the dissemination ofthat data to the respective parties.

In some implementations, account verification procedures can beimplemented. As an example, two small payments can be made to anaccount. To verify the account, the exact amount of the two payments canbe entered by a company. If the amounts match the amounts of the twosmall payments, the account is verified. Other verification methods arealso available, e.g., receipt of a voided check; receipt of a depositslip; manual verification with a bank, etc.

Accounting System Synchronization

When businesses reach a certain scale they often acquire accountingsoftware to facilitate the production of their financial statements.There are hundreds, if not thousands, of options to choose from, andwithin those options, tens of thousands of versions. However, in manycases businesses opt to produce their financial statements by hand, orthrough the assistance of outside accounting personnel or consultants.The simple scale of options, and disparate processes within and acrosseach, prevent businesses from easily interacting with one another in ahighly efficient and automated fashion, as accounting platforms are notstandardized, and even if they were, the lack of connectivity among andbetween them would prevent integration. The UPM-enabled system includesa connected network that is designed, among other things, to enable theeasy integration and distribution of data among and between allbusinesses, regardless of the accounting or ERP software they havechosen, or even in circumstances where they use no accounting softwareat all. In some implementations, the UPM-enabled system can be used asthe electronic accounting system for these small businesses. Forcompanies that do use an electronic accounting system, the informationcontained within the electronic accounting system can be synchronizedwith the UPM-enabled system. For example, data representing vendorlists, buyer lists, receivables, payables, etc., can be integrated intothe UPM-enabled system.

The accounting system synchronization can start with the companyindicating the accounting system that is used by the company. Locationinformation, such as where accounting data files, last used file, etc.,are located, can be provided as needed. For example, the UPM-enabledsystem can determine and/or suggest a location or the user can browseand select the source location. Once the accounting system isidentified, and data files located, the accounting data can be sent tothe UPM-enabled system. After the accounting data is in the UPM-enabledsystem, the UPM data can be synchronized with the company's accountingsystem. As described in greater detail below, synchronization can bedone in various ways. For example, synchronization can be done onexpress demand by the company. In another implementation,synchronization can occur automatically based upon a change in eitherthe company's accounting system and/or the UPM. One advantage of syncingwith the UPM-enabled system is that vendors are able to transmit invoicedata (among other information) to all customers connected to theUPM-enabled system without any meaningful changes to the businessprocesses already designed to uniquely maximize their internalefficiency. This feature is in contrast to circumstances where customersregularly dictate unique invoice and/or data delivery requirements totheir vendors, requiring vendors to modify their business practices toaccommodate these unique requirements. In many instances, theserequirements can only be met by purchasing yet additional softwareunique to the requirements of a specific customer, and paying thirdparty integrators to modify solutions.

In one implementation, a synchronization agent on one or more computingdevices of the company can be used to send and receive data to/from theUPM-enabled system. For example, in the instance where both a buyer andvendor are connected to the UPM-enabled system, and each other on theUPM-enabled system, and both are utilizing syncing functionality, andthe buyer is utilizing auto-syncing functionality (and after syncing ifthe buyer was not auto-syncing) to keep both its accounting systemand/or ERP system in sync with the UPM-enabled system, the act of thebuyer paying an invoice within its accounting or ERP system wouldinstantaneously push payment data to the UPM that would be visible tothe vendor. In addition, the UPM-enabled system would provideinstantaneous notification to the devices preferred by the vendor(email, text, etc.) Upon confirmation of receipt of the payment, thevendor would need only indicate, on the UPM-enabled system, that thepayment had been received, and a sync entry would be triggered, allowingthe vendor to apply the payment within its accounting system without anydata entry and without error. Further, since the UPM-enabled system canserve as a business process management system, in instances where apayment was received from a customer and a discrepancy existed, thevendor would be able to modify the application of the payment on theUPM-enabled system. For instance, if the customer made a payment infull, but took a credit for damages, or a perceived allowance, thevendor on the UPM-enabled system would be able to apply the “shortpayment” to the GL categories that existed (or create new ones thatwould be pushed into their accounting system) within the vendor'saccounting or ERP system (same being visible on the UPM-enabled system),and upon satisfactory categorization of the payment on the UPM-enabledsystem, sync same down to their accounting or ERP system. All of thiscan be done from any internet connected device, at the click of abutton, without any data entry. Using a synchronization agent allows acompany to continue to use its existing accounting system whilereceiving the benefits of the UPM-enabled system. Thus, a company canuse the UPM-enabled system without having to change internal proceduresto accommodate or learn a new accounting system.

Advantageously, synchronization of accounting and ERP data with theUPM-enabled system, which serves as a network of businesses, allows eachcompany to manage its relationships with all of its customers andvendors from the UPM-enabled system. More specifically, rather thanmanaging fifteen different relationships with its customers using acombination of manual and integrated closed loop systems(buyer/vendor-specific), the same company would be able to manage allfifteen relationships within the UPM-enabled system, assuming the buyerswere all connected to the UPM-enabled system. In one place, the vendorwould be able to see the status of all open invoices from one location.Further, the vendor, who itself is likely a buyer, would also be able tomanage its relationships with its vendors, and all without phone calls,data entry duplication or error, and all fully integrated. TheUPM-enabled system, therefore, is far more than an invoice presentmentsolution used by a buyer to communicate invoice status to vendors. It isa network, or ecosystem, of fully integrated (data delivery, receipt,review, dispute, approval, payment and synchronization into disparateaccounting platforms) relationships, which does not require third partyintegrators, expensive new platforms, new business processes across allcustomers and all vendors.

In one implementation, the synchronizing of data requires approval ofthe data that is to be synchronized. Changes to data in the UPM-enabledsystem and the company's accounting system can be noted, but notautomatically synchronized. For example, a synchronization queue can beused to indicate the synchronizations that need to occur based uponchanges to data. For example, a company can create a new invoice in thecompany's accounting system. The synchronization agent can send to theUPM-enabled system data that describes this new invoice. In thisimplementation, the UPM-enabled system does not synchronize this datawith the company's accounting data on the UPM-enabled system. Rather,the UPM-enabled system indicates in the synchronization queue that thenew invoice was created in the company's accounting system, has beenidentified by the synchronization agent and is available to besynchronized with the data in the UPM-enabled system. Data changes madeto the UPM-enabled system's accounting data can also be shown in thesynchronization queue. For example, a company may issue a credit memofrom the UPM-enabled system to a vendor's account using the UPM'sinterface. This change can be shown in the synchronization queue, butwill not be integrated into the customer's accounting system until thecustomer approved the sync, or turns on auto syncing capabilities.Nonetheless, the vendor would be made aware of the credit memoimmediately upon creation by the customer. A customer can review thesynchronization queue and select any of the data changes to sync. Forexample, a customer can select to synchronize all entries in thesynchronization queue. Once selected, the selected queue entries can besynchronized between the UPM-enabled system and the company's accountingsystem.

In another implementation, data can automatically be synchronized asdata changes in either the UPM-enabled system or the existing accountingsystem. In this implementation, when a change in made to any accountingdata in one system, the change is sent to the other system. For example,if an invoice is changed in the existing accounting system, the changeis sent and automatically synchronized with the data in the UPM-enabledsystem. The synchronization agent can send and receive data as describedabove. However, rather than needing express approval to synchronizedata, the synchronization agent can sync received data with thecompany's existing accounting system as data is received. Similarly, theUPM-enabled system can synchronize its data when changes in the existingaccounting system are received from the synchronization agent. Althoughnot entirely eliminated in this implementation, data conflicts can begreatly reduced.

During synchronization, data conflicts can occur between varioussystems. For example, both a buyer and a vendor may change the samepiece of data but to different values. Some changes, however, may not bematerial to a particular party. Because the accounting system data mayhave changes that are not material as far as the UPM is concerned, ahash of the fields that are material is computed, and compared to onegenerated from the UPM-enabled system's data to hide entries from thequeue where only extraneous data has changed. The entry is still writtento the UPM-enabled system, however, because the immaterial data may berequired for display on an invoice or other document generated by theuser. The data can be stored as a collection of name-value pairs thatcan be retrieved when needed. If the accounting package allows for it,the document layout itself can also be synced to and from theUPM-enabled system. A data collision can also occur between materialdata. For example, an amount of an invoice could be modified both in theuser's accounting system, and in the UPM-enabled system, both todifferent amounts and both prior to the last sync (assuming auto syncingwas not enabled). If both of these changes are synchronized, a datacollision can occur since the same piece of data was changed todifferent values. The conflict can be resolved in a number of ways: thechange from either the UPM-enabled system or the accounting system canautomatically trump the other; the latest change can win; or the usercan decide. In one implementation, the conflicting data and anyassociated data can be displayed and a company can expressly indicatewhich change should be synchronized.

As described above, the UPM-enabled system allows integration with abuyer's accounting system. Changes made in the buyer's accounting systemor in the UPM-enabled system can be synchronized with one another. TheUPM-enabled system, however, also allows synchronization with a vendor'saccounting system. Accordingly, the UPM-enabled system integrates theentire invoicing process into the accounting systems of both the buyerand the vendor, regardless of their platform, and without the need forthe purchase of third party adaptive software. In one implementation,the UPM-enabled system uses synchronization agents on both the buyer'sand vendor's computing systems. The UPM-enabled system can send data tothe synchronization agent in a known format, e.g., a common data format.For example, the UPM-enabled system can send data that describes a datachange, e.g., in XML, field=value format, etc. The synchronization agentcan then integrate the data into the existing accounting system. Inanother implementation, the UPM-enabled system can send the changes tothe data in a format that is compatible with the existing accountingsystem. In this implementation, the synchronization agent can simplypass along the data for integration into the existing accounting system.

In yet another implementation, the synchronization agent can extractaccounting data from a software package and convert it to a common dataformat for transmission across a network to the UPM. A synchronizationagent can receive data from the UPM in the common data format andconvert the data into a format for use by a specific accounting system.Various accounting systems can easily be supported through thesynchronization agents. Because the data is transported in a common dataformat, data uploaded to the UPM-enabled system from one accountingpackage can then be downloaded into a completely different accountingpackage. In a typical scenario, the data synced up from one user'saccounting package will be transmitted to another user, who will thenhave the opportunity to review it and make changes if necessary. In oneimplementation, once the second user approves the data, it can be synceddown into their accounting package, even if it is a different version ordifferent accounting package altogether, from that used by the firstuser. Often times this will occur by the data being placed into aseparate outbound queue, so it can be pulled down by the synchronizationagent at a future point in time, although, the process can be automatedbased on user preference and described in greater detail above.Similarly to how the agent can convert accounting package data to acommon data format, it can also write data from the common format backto an accounting package through the same synchronization agent.

The UPM-enabled system can also provide an interface for accessing andmanaging data from UPM. For example, a web interface or a client programcan allow data to be directly input into the UPM-enabled system. Thisimplementation can be used by companies that do not have an electronicaccounting system. Accordingly, there is no need to synchronize the dataas from the company's perspective there is only a single accountingsystem, the UPM-enabled system. The company, however, can take fulladvantage of the features of the UPM-enabled system. In addition, theUPM-enabled system can provide a mobile interface such that mobiledevices can easily access data contained with the UPM.

Once a buyer or vendor has synced their accounting data with the UPM,vendors or buyers can quickly and efficiently obtain a snapshot ofreceivables or payables. In one implementation, the UPM-enabled systemallows a vendor and/or buyer to see all of their outstanding invoices,the due date of the invoices, their buyers willingness to pay invoicesearly, and if so, the applicable discount that would be due. This allowsa vendor or buyer to easily see the current cash flow due them, as wellas the total amount of funds available for acceleration. For example,vendors can use this data to determine how best to access additionalliquidity and how that will impact the vendor's cash flow. As anadditional example, a buyer can see all outstanding invoices that are tobe paid and determine how best to pay the invoices. The various data canbe presented in table format, in an image, in a graphical format, or ina calendar format.

Invoice Management

After a buyer and a vendor for a transaction are registered with theUPM-enabled system, the invoicing process can be fully electronic.Further, the features of the UPM-enabled system allow both the buyer andvendor to continue using their existing accounting system, gain thebenefits similar to those of specialized electronic invoice systems, andgain features not available in the specialized electronic invoicesystems. For example, in one implementation of the UPM-enabled system, abuyer can review an invoice on a computing device or mobile computingdevice. To the extent an error is identified the buyer can select theline item reflective of the error, entering the correct value ($15dollars an hour, rather than $150 dollars per hour), adding a comment toexplain the change, and upon completion, the UPM can immediately delivernotification to the appropriate vendor, e.g., the specific personidentified to receive such notifications, given the customer, amount,etc., of the customer change/dispute. To the extent the vendor agreeswith the change, the vendor can acknowledge acceptance. Uponacknowledgement, if the vendor is a user that syncs the UPM-enabledsystem with their accounting platform, the UPM automatically creates aCredit Memo to push to the accounting platform, through the sync process(which can be automated as described above), eliminating data entry, andensuring an efficient resolution process. Further, the customer can benotified and the invoice value changed per the resolution, appending theinvoice history to include a complete audit trail of the dispute and theresolution. In another example, a customer might receive ten boxes ofglass tumblers. If one box was damaged and all items within the boxbroken, the customer could take a picture of the damaged box on theirphone, select the line item on the invoice representing the ten boxes,edit the line to reflect nine boxes, transfer the photo from their phoneto the line item, possibly adding a comment, and upon completion,notification can be sent to the vendor, and the UPM-enabled system canbe updated to reflect same. In another instance, where the changesdescribed above took place on the UPM rather than a mobile device, thephoto could be attached to the line item. If the damage was discoveredafter the invoice had been synced to the buyer's accounting platform,notification would still be sent to the vendor, but upon acceptance bythe vendor, since the UPM would have knowledge that the invoice hadalready been synced to the customer's accounting platform, the creditmemo that was generated by the UPM-enabled system for syncing to thevendor's accounting platform would also be delivered, via the UPM, tothe buyer, for syncing into their accounting platform. The process cango back and forth if the vendor does not agree with the buyer.

The UPM-enabled system can also be used to provide accounting data in aform and/or format based upon a buyer or vendor's invoice, receipt,approval, payment, etc., processes without requiring the correspondingbuyer or vendor to understand and expressly comply with the processes.For example, buyers often establish unique invoice, receipt, approvaland payment processes the effectiveness of which are based on thestandardization of vendor invoices, or at a minimum, ensuring thatvendors submit invoices with minimum required data and fields. In otherinstances, buyers expressly attempt to minimize the fields that appearon vendor invoices, minimizing accounts payable review timelines. Buyerstypically produce operational manuals to help vendors understand theserequirements. Practically, buyers have little ability to control thebilling practices of their vendors, particularly their small andinfrequent vendors. As a result, they often receive invoices that areinconsistent with their requirements. To encourage compliance buyerssometimes charge vendors penalties for sending invoices that areinconsistent with their requirements. Another common strategy is tosimply refuse to process nonconforming invoices. Unfortunately, thiscommon problem, and its unfortunate consequences, causes everyone tolose.

In one implementation of the UPM-enabled system, buyers are able toestablish universal invoice acceptance criteria. For example, a buyercan indicate the fields that are required to be on an invoice. The buyercan also indicate what fields are not needed and should not be part ofthe invoice sent to the buyer. When the UPM-enabled system receivesinvoice data from a vendor for the buyer, the UPM can ensure that thedata requested by the buyer is contained in the data received from thevendor. If any data is missing, the UPM can inform the vendor to provideadditional information. As part of this process, the UPM can format datareceived from a vendor and ensure that the data matches the criteriaprovided by the buyer. Accordingly, the UPM-enabled system can ensurethat the buyer receives the desired data and remove any data provided bythe vendor but not needed by the buyer.

Alternatively, buyers can establish standards for different types ofpurchasing. For instance, inventory purchases might be required to beaccompanied by a purchase order number while transportation invoices bya proof of delivery or PRO number. These standards can then be used bythe UPM-enabled system to ensure a vendor's compliance, nearlyeliminating the need for vendor training. For instance, the UPM, duringthe sync process, as described in greater detail below, is able toidentify the fields being sent by the vendor and can ensure that allrequired fields are present. To the extent the UPM-enabled systemidentifies an invoice without required data, the invoice can beidentified as missing required fields, as presented in the sync queue,as described in greater detail below. In the case of a missing dataelement the vendor can be made aware, prior to delivery of theirinvoices, that the invoices are deficient and cannot be delivered. Thevendor can then append the invoice from within the sync queue, sendingit on to the customer for review and approval. This functionality ishighly valuable, as it can be done from anywhere, at any time. For thoseusers using middle market accounting platforms that do not allowinvoices to be “amended”, it eliminates the need to void and re-createinvoices. Alternatively, for users with lower end accounting platformsthat allow invoices to be amended, the user could add detail to theirinvoice from within their accounting system, re-syncing it with the UPMfor delivery to their customer. Additionally, the UPM-enabled systemalso has the ability, during the sync process, to ignore extraneousfields, only transmitting into the buyer's accounting system therelevant fields. Additionally, all fields can be delivered to the buyer,while only relevant or required can be presented to users for review, orautomatically integrated within the buyer's accounting platform.

As a further example, a buyer can provide the UPM-enabled system willrules on how an invoice from a vendor can be automatically transformedinto a bill for the buyer. FIGS. 10-16 are screenshots of a userinterface in accordance with an illustrative implementation andillustrate mapping an invoice to a bill. FIG. 10 illustrates an invoice1000 from a vendor. The invoice 1000 contains various information suchas the invoiced items, costs for the items, quantity of items, and atotal balance due. A buyer can see this invoice 1000 from within theUPM-enabled system and can approve items in the invoice 1000. FIG. 11illustrates approving all the items in the invoice 1000. If an item wasdisputed, the UPM-enabled system can facilitate the dispute process,which is described in greater detail below. Buyers can view the invoice1000 through the UPM-enabled system, but can also generate a bill fromthe invoice 1000. FIG. 12 illustrates a bill that is generated from theinvoice 1000. Buyers can create rules that convert or map invoice data,which is provided from the vendor, into bill data, which is in a formatuseful for the buyer. For example, the buyer can create a defaultgeneral ledger (GL) account code that is associated with a particularvendor. The default GL account code can then be associated with eachinvoice item. The buyer can also create a different GL account codemapping for particular invoice items. FIG. 13 illustrates variousinvoice items mapped to various GL account codes. The UPM-enabled systemcan remember these mappings and on future invoices automatically assigninvoice items to the appropriate GL code.

FIG. 13 also illustrates converting a vendor-supplied quantity into abuyer quantity. In the illustrated example, the vendor has invoiced onepallet of Hammermill® paper, which contains ten cases of paper. Thebuyer can indicate that the one pallet of paper should be treated as tencases instead of a single pallet. This conversion can be saved andautomatically applied to future invoices from the vendor. FIG. 14illustrates a bill with ten cases of paper rather a single pallet ofpaper. The ten cases can be divided in various ways. For example, in theexample bill, the cases are split into two bill items, each representingfive cases. The two bill items can be treated independently from oneanother. For example, the two bill items can have different GL accountcodes, descriptions, classes, etc.

Based upon the various mapping/conversion rules, a bill can begenerated. The UPM can generate a bill based upon rules provided by thebuyer. For example, the buyer can indicate the fields that should appearon the bill. FIG. 15 illustrates an example of a draft bill 1500 basedupon the invoice 1000. As can be seen in the draft bill 1500, the tencases of paper that were split are shown differently. Five cases areshown as an expense item 1502 and five cases are shown as an inventoryitem 1504. In addition to splitting items, the UPM allows invoice itemsto be merged based upon the buyer's preference. For example, expenseitems 1506 and 1508 can be merged together since both items are expenseitems related to pens associated with the break room. To merge the items1506 and 1508, the items are selected and the merge lines button isselected. FIG. 16 illustrates the merged expense items 1602. Once thebuyer is satisfied, a bill can be generated from the draft bill 1500 byselecting the create bill button. If the buyer has their own accountingsystem, the bill can be synchronized into the buyer's accounting systemas described above.

The UPM-enabled system can also facilitate payment of invoices. FIG. 3is a timing diagram 300 of paying an invoice using a universal paymentmodule in accordance with an illustrative implementation. The timingdiagram 300 illustrates operations performed in the payment process.Additional, fewer, or different operations may be performed, dependingon the embodiment. The order of the operations may also be different,depending on the particular implementation. In the timing diagram 300,both a vendor 202 and a buyer 206 have previously registered with theUPM 204 and have connected with one another through invitation. Thevendor 202 can create an invoice (operation 302), for example byentering a new invoice into an existing accounting system. Oncesynchronized, the UPM 204 contains data associated with the invoice,which is presented to the customer for review. If the customer is a verylarge business with an existing complex work flow approval process, thedata from the vendor's invoice can simply flow through the UPM 204 intotheir existing work flow management process. In one implementation, theinvoice is sent based upon synchronizing the invoice data. For example,the vendor 202 can enter the invoice into the vendor's accounting systemand indicate that the invoice is to be sent to the buyer 206 byselecting a transmit button that can be added to the vendor's accountingsystem. Still, in another implementation, once invoices are entered intothe vendor's accounting system, the sync can be triggered, or occurautomatically, and the invoice will automatically be reflected in thebuyer's screen with the UPM-enabled system. In another implementation,the UPM 204 does not send the invoice to the buyer 206 uponsynchronization. Rather, the vendor 202 can, at a time aftersynchronization, use the UPM 204 to send the invoice to the buyer 206.

The buyer 206 can then approve the invoice on the UPM 204 (operation306). Upon approval, the vendor is immediately notified, and theinvoices, within the vendor's screens on the UPM-enabled system willreflect the approved invoice status. In another implementation, thebuyer can sync invoice prior to approval, approving same within theirexisting accounting system. To the extent that their system can capturethe invoice status, the same will be reflected within the UPM-enabledsystem upon sync. In another implementation the customer can createrules, using the UPM's workflow engine and rules engine, to approveinvoices in an automated fashion. After approval, the approvalnotification can be sent to the vendor 202 (operation 308). At a latertime, the buyer 206 can pay the invoice. In one implementation, paymentof the invoice can be accomplished using a written check. Informationabout the payment, e.g., date of mailing, check number, amount, etc.,can be sent to the UPM-enabled system (operation 310) automatically,through the sync process. This data is then available to the vendor 202(operation 312).

In another implementation, the buyer 206 can pay the vendor 202 directlyusing account information of both the buyer 206 and vendor 202 containedwithin the UPM-enabled system. In this implementation, the buyer 206 canrequest that one or more invoices be paid in full or partially out of anaccount associated with the buyer 206. The buyer 206, however, is notrequired to know any account information of the vendor 202. Instead, theUPM 204 has the account information of the vendor 202 needed to completethe electronic payment. The UPM can determine the accounts based upondata provided by the buyer and vendor. For example, a buyer can indicatea default account from which invoices are to be paid and a vendor canindicate a default account to receive payment. Of course, the buyerand/or vendor can change these accounts for particular invoices,customers, etc. Once the account information of the buyer and vendor areknown, the UPM-enabled system can facilitate the payment in variousways.

In one implementation, electronic payment can be achieved using ICLs,e.g., a Check 21 compliant process. The UPM-enabled system can determinethe accounts associated with paying an invoice. If the UPM-enabledsystem has an agreement with the vendor's financial institution thatallows ICLs, the UPM can create an ICL transaction based upon the one ormore invoices to be paid. In this implementation, a buyer is providedwith information regarding the payment of invoices. The buyer can selectan account to pay the invoices and create a check by affixing theirsignature and telling the UPM-enabled system to pay the one or moreinvoices, e.g., by clicking on a pay button. In one implementation, thesignature is affixed by the UPM-enabled system after receiving thebuyer's instructions to affix their signature. The buyer, therefore, isdetermining the amount of the payment, the vendor, and the date ofpayment. The check can then be sent to the UPM-enabled system. In oneimplementation, the UPM-enabled system can dynamically present an imageof the check for the buyer to review, including affixing the buyer'ssignature, as requested by the buyer. The check can include languageindicating that the check is in all respects a legally binding check incompliance with the UCC. In one implementation, the UPM-enabled systemcan then print and image the check. In another implementation the checkis not printed. Once the UPM-enabled system receives the buyer's check,the UPM-enabled system can deliver the check to the vendor via ICL. TheUPM-enabled system, through its network of financial institutionrelationships, can then create an image cash file for submission to thevendor's financial institution. This image cash file can includedeposits for numerous vendors of the financial institution. Within theimage cash file will be an image cash letter unique to the payments madeby the customers of the vendor. Through the ICL process, a payment canflow from the buyer through the UPM-enabled system, directly to thevendor's account, in cleared funds, in as little as minutes.

In one implementation, the image cash file can be uploaded periodicallyand results in the initiation of transfer of funds between the buyer andthe vendor. In another implementation, the file can be sent to thebanking institution immediately after the file is generated. Vendors,therefore, receive their payments electronically within minutes or hoursinstead of days, without the need of paper checks, which must still bedeposited to their financial institution prior to accessing the funds.In addition, the vendor's confidential financial account information isprotected since it is never disclosed to the buyer 206. In oneimplementation, the UPM 204 can be accessed via mobile devices.Accordingly, the buyer 206 can interact with the UPM 204 through amobile device and initiate payment through a single click via a mobiledevice.

Before an ICL payment can be made directly from a buyer to a vendor,there must be an agreement with the vendor's financial institution thatallows the UPM-enabled system to deliver a buyer's check to the vendor.Using the vendor's financial account information, the UPM-enabled systemcan determine if a buyer to vendor ICL payment is possible. If such adirect ICL payment is not possible, the UPM-enabled system can stillfacilitate the payment in an efficient manner. For example, in oneimplementation, the UPM-enabled system can make two transactions, an ICLand an ACH, that reduces the amount of time for funds to be receivedcompared to a traditional ACH payment from a buyer to a vendor. TheUPM-enabled system can first use an ICL transaction into an accountassociated with the UPM-enabled system at the vendor's financialinstitution. The account associated with the UPM-enabled system is notthe vendor account, but rather an account that, based upon an agreementthe financial institution, can make ICL deposits. The ICL transactionincludes the buyer's check being delivered to the vendor via the accountassociated with the UPM-enabled system. The buyer's payment is depositedinto the UPM account, for the benefit of the vendor, and is thentransferred to the vendor's account via ACH. In one implementation, theUPM-enabled system can initiate the ACH transfer after the ICL hascleared. Alternatively, the UPM-enabled system may not wait for paymentto clear before initiating an outbound ACH to the vendor's account.Because the UPM-associated account and the vendor's account are with thesame financial institution, the ACH payment can be handled more quicklythan an ACH payment between two different financial institutions.

If the UPM-enabled system does not have an associated account at thevendor's financial institution, the UPM can use a two-transactionprocess still to deliver the funds to the vendor. In thisimplementation, the UPM-enabled system can initial an ICL payment fromthe buyer's account to a UPM account at a financial institution otherthan the vendor's financial institution. Once the buyer's funds havebeen cleared, the UPM-enabled system can initiate an ACH payment to thevendor's account.

In some implementations, the UPM 204 can verify the deposits. Forexample, a banking institution can provide data concerning the depositssent by the UPM 204. Exemplary data includes the total number ofdeposits made, the total amount deposited, etc. The UPM 204 can compareits data with the data from the banking institution for anydiscrepancies.

At any time during the invoicing process, the buyer 206 or vendor 202can determine the status of the invoice by simply querying theUPM-enabled system. In either case, the status of the invoice can bedetermined without requiring a call to the other party. In addition tobeing able to determine a status of an invoice efficiently, the UPM 204allows for efficient changes to invoices. FIG. 4 is a timing diagram ofa change request process using a universal payment module in accordancewith an illustrative implementation. Additional, fewer, or differentoperations in the process may be performed, depending on the embodiment.The order of the operations may also be different, depending on theparticular implementation.

Similar to FIG. 3, an invoice is sent by the vendor 202 to the buyer 206through the UPM 204 in the UPM-enabled system (operations 402 and 404).The buyer 206, however, notices a mistake or wishes to change theinvoice in some way. Instead making a phone call or emailing the vendor,which may necessitate the vendor voiding the invoice and sending a newinvoice, the buyer 206 can request a change to the invoice by sendingthe requested change to the UPM 204 (operation 406). For example, thebuyer 206 can make a change to invoice data displayed through theinterface of the UPM 204. The requested change can then be sent to thevendor. Alternatively, the vendor 202 can request a change to aninvoice. Upon receipt of the change request (operation 408), the vendor202 can send an approval of the change back to the UPM 204 (operation410). If the vendor 202 did not approve the change, an indication of therejection can be sent back to the buyer 206 through the UPM 204. At thispoint, the buyer can ignore the rejection and simply pay the amount theybelieve is correct or pay the originally invoiced amount. Upon receiptof the approval of the requested change (operation 412), the buyer 206can pay the updated invoice (operations 414 and 416) in a similar way asdescribed above in regard to FIG. 3′s payment of the invoice. Based uponchanges to invoices, the UPM-enabled system can determine if a creditmemo should issue and be extended to the buyer 206 as described indetail above.

Early Payment of Invoices

Buyers sometimes have the ability to pay invoices before their due datesand vendors sometimes would like or be willing to be paid prior to thedue date of their invoices. To entice buyers to do this, vendors canoffer a discount on the invoice if the invoice is paid early. Due to thetime needed to negotiate terms, vendors have adopted set rules thatapply generally across most if not all of their invoices. For example,2% 10 net 30 is a common set of terms where a buyer can take a 2%discount on an invoice if paid within 10 days. If the invoice is notpaid within 10 days, the total amount is due within 30 days. These termsare not negotiated on an invoice-specific basis for most invoices as theamount of time and resources needed to agree to terms would not bejustified by the savings. Accordingly, known agreements, such as 2% 10net 30, are used.

The UPM-enabled system, however, allows for efficient early paymentsthat are not bound by generally acceptable terms. In one implementation,a buyer can request that a vendor accept early payment for a particulardiscount, on a particular invoice, or a group of invoices, through theUPM-enabled system. The vendor can then review all request for earlypayment within the UPM 204 and accept early payment from one or morerequests. In another implementation, companies, in their capacity asbuyers, can create discount graphs that describe the discounts they arewilling to take for early payments of an invoice to a vendor, or acceptfor early payment from a customer. Discount graphs can be based upon anyformula, curve, etc.

These discount graphs can be unique to a particular buyer/vendor, aparticular invoice, invoices of certain amounts, etc. The discountgraphs can be used by the UPM 204 to automatically accept early paymentrequests through matching the request for early payment with theappropriate discount graph. That is to say, if a vendor has indicated,through the creation of a discount preference, a willingness to acceptearly payment for a fee of 2%, and a buyer of the vendor has indicated awillingness to pay early for a fee of 2%, the UPM-enabled system canautomatically accept and notify the buyer of the vendor's acceptance.Automatic acceptance of the request can be controlled throughpreferences in the UPM-enabled system. For example, a request thatmatches the appropriate discount graph can be indicated as matching butrequire the vendor's explicit approval before accepting. In anotherimplementation, the UPM-enabled system can automatically accept therequest for particular buyers/vendors, for invoices whose amounts arebelow a particular amount, etc. In another implementation, the vendorneed only indicate through, or to, the UPM-enabled system the totalfunds needed and the UPM automatically notifies the buyer that a matchhas been made and can be accepted through the act of payment. In oneimplementation, the payment can occur in the simplest implementationthrough the act of selecting the pay button. The act of selecting thepay button being acknowledgement by the buyer that they wish to createan electronic check, affixing their signature thereto, from theirdesignated account to the account of the vendor through the UPM-enabledsystem. Additional examples of discount graphs and the use of discountgraphs for both buyers and vendors are described in greater detailbelow.

In another implementation, the vendor can indicate a need for a specificdollar amount and if no matches to their discount preferences were ableto be made automatically, the UPM-enabled system can present to thevendor the most proximate matches to their preferences, allowing thevendor to request early payment from the next most acceptable buyeroffer. In yet another implementation the vendor can indicate theirwillingness to accept early payment from the buyer if the fee wasadjusted to an alternative amount. The buyer would then have the abilityto accept the alternative offer, accepting through the act of payment,or begin a negotiation cycle. All negotiation cycles ending based eitheron timetables established by either the buyer or vendor or upon paymentby the buyer.

The UPM-enabled system can enable a buyer to pay invoices early, withlittle to no friction or inefficiency. FIG. 5A is a timing diagram ofrequesting early payment process of an invoice in accordance with anillustrative implementation. Additional, fewer, or different operationsin the process may be performed, depending on the embodiment. The orderof the operations may also be different, depending on the particularimplementation. Similar to FIG. 3, an invoice is sent by the vendor 202to the buyer 206 through the UPM 204 (operations 550 and 552). The buyerapproves (operation 554) the invoice and an indication of this approvalis sent to the vendor (operation 556) and visible through the UPM. Atsome point, the buyer 204 decides that they are willing to pay one ormore invoices from the vendor 202 prior to the one or more invoices'respective due dates. The buyer 206 can send a notification of itswillingness to pay early, at a corresponding fee to the vendor 202,through the UPM (operations 558 and 560). The vendor 202 can then acceptthe early payment request by sending a request for early payment to thebuyer through the UPM 204 (operations 562 and 564). The invoice can thenbe paid (operations 566 and 564) in a similar way as described above inregard to FIG. 3's payment of the invoice. For example, if accepted bythe vendor, the UPM-enabled system can notify the buyer and the buyercan make payment via electronic check via the UPM from anywhere, at anytime, with the click of a button. For example, as describe in greaterdetail throughout, payment can be made by a one click payment or amulti-click payment workflow with varying levels of checks and balances.

As another example, the buyer 206 can communicate on the UPM-enabledsystem its willingness to pay an invoice early, if within 5 days of theinvoice date, for a 3% discount or a 1.5% discount if paid after 5 daysof the invoice but prior to its due date. The amount of the discountseen by the vendor 202 can be automatically updated based upon the ageof the invoice. For example, the discount in the above example wouldautomatically be reduced from 3% to 1.5% if the vendor 202 did notaccept the early payment request within the 5 day timeframe. The vendor202 can accept the early payment request by sending a request for earlypayment to the buyer through the UPM 204, and the invoice can then bepaid in a similar way as described above in regard to FIG. 3's paymentof the invoice.

The vendor 202 can also approve the buyer's early payment request butrequire that the buyer 206 pay the invoice within a specified timeperiod. For example, the vendor's approval can be valid for a period oftime, e.g., 24 hours, 48 hours, etc, in which the buyer must sendpayment. If the buyer 206 does not send payment in that period of time,the vendor's approval can be automatically revoked by the UPM 204. TheUPM 204 can notify the buyer 206 that the vendor's approval is no longervalid.

In one implementation, the vendor can tell the UPM-enabled system toaccept early payment requests based upon approval criteria. For example,the vendor can indicate that all early payment requests from particularbuyers less than a certain amount with discounts below an identifiablethreshold should be accepted. In addition, the vendor can limit theautomatic acceptance of early payments by limiting the total amountwhich can be accepted within any given period of time. In oneimplementation, a vendor can have the UPM-enabled system automaticallypay an accepted early payment request based upon the approval criteria.

The UPM 204 can also allow buyers to offer unique and customizable earlypayments options to its vendors, which through the UPM can be visible onan invoice-specific basis to all vendors. These terms can be unique to avendor, a purchase order, an invoice, or a category of vendors, and canbe tied to any metric designed by the buyer. For instance, the buyer mayestablish a linear daily declining discount rate, from 3% at 30 daysearly to 0% on the due date. Further, the buyer may establish a floorrate, not less than 1.25% of the invoice amount. Still differently, thebuyer may establish fees based on buckets of time (invoices paid 25-30days early are associated with a discount of x, and 20-24 days early areassociated with y discount). Still, differently, buyers may establishterms that are offered to unique classes of vendors (minority- andwomen-owned businesses).

As to the vendor, given that the UPM-enabled system includes connectionsto a network and vendors can see all customer relationships in onelocation, vendors can manage their access to capital in a truly uniqueway, as they will always be able to see the least expensive termsavailable, and can select those terms. That is, the vendor can seeoffers from various buyers willing pay invoices early and the discountthey are requesting. A vendor can then request early payment of theinvoices, in the amount they need, at the time they need for a fee thatthey are willing to accept, all, having been optimized by competitionacross their buyers. Since the early payment of invoices creates a newsource of capital/liquidity for vendors, and the need and importance ofcapital/liquidity can differ at different times (missing payroll forlack of liquidity may be considered a bigger problem than not being ableto pay certain bills on time) the vendor can be provided many earlypayment options. For instance, the vendor may opt to request, via theUPM-enabled system, early payment in the amount needed for the lowestpossible discount. Alternatively as described in greater detail below,the vendor may opt to select early payment from the vendors with thegreatest likelihood of fulfilling their payment request on time, the UPMserving as the analytics engine to evaluate, rate and predict customerperformance. Still alternatively, the vendor may select to extend earlypayment requests to the buyers (a combination of buyers may be requiredto fulfill the total amount needed by the vendor) that are able tofulfill the vendor's request, at the lowest possible discount. Stillfurther, the vendor, in need of liquidity with a great deal ofcertainty, but not wanting to pay higher discounts unnecessarily, coulduse the capability within the UPM-enabled system to extend additionrequests to successive buyers, or to invoices within buyers, who areoffering higher rates, but only after providing a window of time for theinitial request, on lower priced invoices, to pass. For instance, ifbuyer one was offering to pay invoice 123 with a value of $5,000 for adiscount of 1%, and invoice 1234 with a value of $3,000 for 3%, andbuyer two was offering to pay invoice 321 with a value of $1000 for adiscount of 1.5%, and invoice 3214 with a value of $6,000 for a discount2.5%, the vendor could ask the UPM-enabled system to optimize, using auser friendly interface, for cost and speed while finding $6,000 for thevendor, with a further request increment of 20 minutes. In thiscircumstance an early payment request would immediately be placed(either automatically, or presented to the vendor for approval) oninvoice 123 from buyer 1 and invoice 321 from buyer 2. If 20 minutesexpired, and neither buyer 1 nor buyer 2 fulfilled the request, afurther request would be extended to invoice 3214 from buyer 2 (whichcarries a higher rate). If buyer 2 fulfilled the request, all otherrequests would immediately be terminated, the buyers being notified thatanother buyer had fulfilled the request. In another implementation if noother buyer had fulfilled their request, and buyer 2 attempted to payboth outstanding requests, totaling $7,000, buyer 2 would be notifiedthat the vendor had limited the total funds payable early to $6,000.Further, if another buyer fulfilled the $5,000 request, the $6,000invoice could be automatically deselected by the UPM. Still anotheroption is for the UPM-enabled system to extend early payment requests,in potential satisfaction of the vendor's request, to multiple buyerssimultaneously, in an amount that in aggregate will exceed the fundsneeded. However, in this first-to-fund scenario, the request will beimmediately withdrawn as soon as any one, or series of buyers inaggregate, fulfills the amount identified as being needed by the vendor.

Just as a buyer can notify vendors of their willingness to pay invoicesearly for a discount, vendors can notify buyers of their willingness toaccept early payment for a discount. FIG. 5B is a timing diagram ofrequesting early payment of an invoice in accordance with anillustrative implementation. Additional, fewer, or different operationsin the process may be performed, depending on the embodiment. The orderof the operations may also be different, depending on the particularimplementation. Similar to FIG. 3, an invoice is sent by the vendor 202to the buyer 206 through the UPM 204 (operations 502 and 504). The buyerapproves (operation 506) the invoice and an indication of this approvalis sent to the vendor (operation 508). At some point, the vendor 202decides that they would like to receive payment of one or more invoicesfrom the buyer 206. The vendor 202 can send a request for early paymentto the UPM 204 (operation 510). This request can be sent to the buyer206 (operation 512). To entice the buyer 206 to make an early payment,the vendor 202 can give the buyer 206 a discount on any invoices paidearly. For example, the vendor can give the buyer 206 a 3% discount ifthey pay within 5 days of the invoice or a 1.5% discount anytimethereafter. The amount of the discount seen by the buyer can beautomatically updated based upon the age of the invoice. For example,the discount in the above example would automatically be reduced from 3%to 1.5% if the buyer did not accept the early payment request within the5 day timeframe. The buyer 206 can accept the early payment request bysending payment of the invoice. The invoice can be paid (operations 514and 516) in a similar way as described above in regard to FIG. 3'spayment of the invoice.

As another example of early payment requests, using the UPM-enabledsystem, a vendor/buyer can request early payment from a number ofbuyers/vendors. As an example, a vendor can have a business need toraise a certain amount of money, $4,500, in a particular time frame. Asa vendor is likely to have outstanding invoices to a number of buyers,the vendor can raise any needed funds by requesting early payment ofmultiple invoices from multiple buyers or by accepting one or morerequests to accept early payment from one or more buyers.

FIG. 6 illustrates a listing of invoices 600 that are available forearly payment in accordance with an illustrative implementation.Continuing the example of a vendor wanting to raise $4,500, the listingof invoices 600 in FIG. 6 illustrates outstanding invoices for aparticular vendor. The vendor may have additional outstanding invoicesthat are not eligible for early payment. Accordingly, these invoices arenot shown in FIG. 6.

To raise $4,500, the vendor can request early payment for each of theseinvoices. Assuming that a number of buyers accept the early paymentrequest, the vendor could raise more than the needed $4,500. The vendormay want to avoid early payment of invoices that would result in thereceipt of funds greater than $4,500, avoiding an unneeded discount. Forexample, after raising the $4,500, the vendor may want to wait the termof the invoice to collect the entire amount of the invoice without adiscount.

To minimize the amount of discounts taken by the vendor, the UPM-enabledsystem can determine an order to request early payments. For example,the UPM can the sequence with which to request early payment in such away as to minimize discount fees to the vendor. The UPM can determinethis sequence based upon a number of factors. For example, the UPM cancalculate the order of invoices based upon the best chance of the neededfunds being paid within a timeframe. Prior to generating the listing600, the vendor can provide a preference for certainty over cost. Forexample, following our current example, the vendor can indicate the$4,500 is needed immediately, with a very high level of certainty. Usingthis information, the UPM-enabled system can calculate a predication ofa buyer's acceptance of a request for early payment. For example, usinghistorical acceptance figures, the UPM can determine how likely a buyeris to accept an early payment request for an invoice on a given day.Historical data can include not only historical acceptance figures, butother historical accounting data. As an example, if a buyer processespayroll every two weeks, the buyer may be less likely to accept an earlypayment request during a payroll week. Other examples include otherperiodical payments such as taxes, rent, etc. Further, outstandinginvoices of a buyer can be taken into consideration. If a buyer has tomake a large payment based on other outstanding invoices, the buyer maybe less likely to pay another invoice early. Using a combination of anyof this data, and data available externally, like bank creditavailability, access to funds from the customer's customers, in thecustomers capacity as a vendor, the UPM can calculate an acceptanceprediction.

Using the acceptance prediction, the UPM-enabled system can determine anorder in which to request early payment. For example, the UPM cancalculate an ordered list based upon chance of acceptance. FIG. 7illustrates such an ordered list 700 of invoices for early payment inaccordance with an illustrative implementation. In this case, theinvoices shown in FIG. 6 are grouped and ordered based upon thelikelihood of acceptance of early payment. In the illustratedimplementation, the chance of success is calculated as the simpleprobability of all early payment requests of invoices within a groupbeing accepted based on historical behavior patterns. In otherimplementations, other probabilities can be used, e.g., weightedprobability based upon invoice amount, reduction of probabilities basedupon number of invoices, etc. Using the simple probability, theUPM-enabled system can calculate that the first group 702 consists ofinvoice 1010 (606). This invoice is the only invoice in the group asacceptance of this single invoice will raise the needed $4,500. Inaddition, the chance that this invoice is accepted for early payment is61.3%. The next group 704 consists of invoices 1006 (602) and 1007(604). These two invoices are next in the list since there is a 60.6%chance that both early payment requests associated with these invoiceswill be accepted. If both invoices are paid early, the needed $4,500will be paid. Group 706 is next in the list and includes invoices 1007(604) and 1001 (606). If invoice 1001 (606) and invoice 1007 (604) areboth paid early the entire $4,500 will be raised. Using the acceptancepredication value, the UPM can calculate that there is a 39.7% chance ofacceptance of both. The list 700 does not include invoice 1002 (610). Inone implementation, the invoice 1002 can be filtered out of the invoicesbased upon its low acceptance predication of 5.7%. In addition, if onlyfull invoice amount are used, invoice 1002 can be filtered as it wouldtake an unneeded discount, since no combination of invoices needs$99.00. In other words, another combination would raise the needed$4,500 and the $99.00 if paid early would result in an unnecessary 1%discount.

In another implementation, the list can be ordered based upon thediscount. In this implementation the order of the list would bereversed. The order of the groups would be 706, 704, 702 based upon thecalculated discount for the group. In yet another implementation, thelist can be ordered based upon a combination of the discount and theacceptance rate. Further, the discount and the acceptance rate can beweighted prior to being combined.

Based upon an order listing, a vendor can request that the UPM-enabledsystem request early payment of the invoices in the order of the list700. For example, if a vendor wanted to raise $4,500 but minimize theamount of discount given, the UPM-enabled system can request earlypayment of invoices 1007 and 1001 first. Then after a predeterminedamount of time, early payment of invoice 1006 can be requested. Earlyrequest of payment for invoice 1007 would not be needed since it wasalready requested previously. The same or different amount of time canpass before the UPM requests early payment of invoice 1010. Staggeringthe requests for early payment based upon the ordered list 700 canincrease the chance of raising the $4,500 for the minimum discount.

Optimizations of Early Payment of Invoices

In one implementation, a buyer can indicate that it will pay or willpartially pay an invoice. In previous systems, partial pay wasimpractical as it required time to agree to terms and to record multipleentries into the accounting system. The UPM-enabled system eliminates orremoves these inefficiencies by creating a frictionless transaction.Without the UPM-enabled system, early payment or partial payment of aninvoice required an expensive check print process that includes humaninteraction to agreeing to terms, printing a check, mailing a check,updating an accounting system to note that an invoice was only partiallypaid and that the remaining balance was due at some other date.Partially paying an invoice duplicates some of these steps, e.g.,agreeing to terms, printing and mailing a check, etc. Accordingly,parties typically do not partially pay invoices due to theseinefficiencies. The UPM-enabled system, however, can remove theseinefficiencies and given the seamless nature of the UPM, partialpayment, in conjunction with accounting system integration through theUPM, can be made easily and efficiently. The UPM-enabled system,therefore, facilitates partial payments and allows buyers and vendorsgreater control and options of how invoices are paid. Accordingly, if abuyer is willing to partially pay an invoice, the UPM-enabled system canrequest only partial payment of an invoice. In this case, theUPM-enabled system could request a partial payment of $4,500 for invoice1010 instead of the entire amount as shown in FIG. 6. This featureallows a vendor to raise only the amount of capital needed at adiscount. Any unpaid remainder can be paid by the buyer at a later timewith a smaller or no discount.

Using partial payment of invoices, in another implementation, multipleearly payment requests may be sent to the buyer for the same invoicebased upon discount rates. For example, using the invoice data in FIG.6, if a vendor wanted to raise $3000 the vendor can first request earlypayment of invoice 1001 and also early payment of $1000 of invoice 1006.If after a certain period of time the requests for early payment havenot been accepted, the UPM-enabled system can request that the entireamount of invoice 1006 and $1500 be paid from invoice 1007. After yetanother period of time, if the needed funds have not been raised, theUPM-enabled system can request any needed funds from invoice 1007. Forexample, if no buyer accepted the request for early payment, the entire$3000 can be requested to be paid early from invoice 1007.Alternatively, if the buyer associated with invoice 1006 agree to paythe invoice early, the UPM-enabled system could request the needed $1530from invoice 1007.

The ability to partially pay an invoice can change the order of alisting of early payment requests. For example, in group 604, invoice1006 can be requested for early payment prior to invoice 1007 due to thediscount rates. If early payment of invoice 1006 is accepted prior torequesting early payment of 1007, the vendor can request that $3,030 bepaid toward 1007 instead of the full amount.

The UPM-enabled system can also expire requests for early payment. TheUPM can automatically terminate any outstanding early payment requestsonce the needed amount has been accepted. For example, in the listing600, if early payment has been requested on all invoices and if theearly payment request for invoice 1010 was accepted, all other earlypayment requests can be terminated. Accordingly, buyers can have anincentive to quickly agree to any acceptable early payment requests,since the early payment request can be cancelled based upon anotherbuyer accepting an early payment request from the vendor.

The UPM-enabled system can also allow conditional acceptance. Forexample, in the listing 600, payment of invoice 1007 with either invoice1006 or 1001 would result in the needed $4,500. However, payment ofinvoices 1006 and 1001 together is not ideal since payment of invoice1007 is still needed to reach the $4,500 goal. To avoid this, the UPMcan make the acceptance of an early payment request conditional. Forexample, acceptance of early payment for invoice 1006 or 1001 can beconditional on the acceptance of invoice 1007.

FIG. 8 illustrates a discount graph 800 in accordance with anillustrative implementation. This graph 800 can be used to determine ifthe company is willing to accept an early payment request. That is, if arequest for early payment matches the data in the graph 800, it can beassumed that the company will accept the early payment request. In oneimplementation, the company can have the UPM-enabled systemautomatically accept the request for early payment based upon the datain the graph 800. The graph can be associated with a company's buyers orvendors.

For example, the graph 800 can be associated with a buyer's vendors andindicate the discounted amount the buyer is willing to pay a vendor forearly payment. In addition, the UPM-enabled system can use this table toautomatically accept early payment requests for the buyer from a vendor,without requiring any additional user interaction. The graph 800indicates that the company is willing to pay an early invoice within thefirst five days if the vendor is willing to give the company a 4.0%discount on the invoice. As the invoice ages, the discount the companyis willing to charge is lowered. The graph 800 illustrated resembles astep graph. A discount graph, however, can be any curve, function, etc.

Alternatively, the graph 800 can be associated with a vendor's buyersand indicate the discounted amount the vendor will accept from a buyerfor early payment. The UPM-enabled system can use this tableautomatically to accept requests for early payments from a buyer if thevendor has indicated that the UPM-enabled system can automaticallyaccept requests for early payments. In addition, a vendor can set updifferent discount charts for different criteria. For example, a vendorcan set up a less costly discount graph for preferred buyers. The amountof the invoice can also be used to determine the appropriate discountchart. A vendor may give a larger discount to invoices that are above acertain dollar value. The type of items on the invoice can also be usedto determine the appropriate chart. If an invoice is for items with alarge profit margin, the vendor can use a discount chart with higherdiscounts. Conversely, the vendor can use a discount chart with smallerdiscounts for invoices that have small profit margins. The UPM-enabledsystem can determine which chart is appropriate based upon the currentinvoice and use the correct chart. Once the correct chart has beenselected, the chart can be used to determine if early payment should beaccepted. Other criteria can also be used to determine if early paymentshould be accepted. For example, data can be used from the integrationwith the company's accounting systems, e.g., margins, vendor categories,future payouts, payables, etc.

Buyers can also use this data to create discount charts that indicatethe discount they will accept for early payment. For example, if a buyerknows that a vendor has larger margins, the buyer can charge more to payan invoice early. In some instances, two companies will be both buyersand vendors to one another. A different discount chart can be used forthese instances. For example, a smaller than normal discount can be usedto foster the existing business relationship. In this implementation,the UPM-enabled system can determine which chart is appropriate basedupon the current invoice and use the correct chart. Once the correctchart has been selected, the chart can be used to determine if earlypayment should be accepted.

Early Payment of Invoices Marketplace

There are at least three different options for an early payment ofinvoices marketplace. First, finance players can register on theUPM-enabled system. The buyers are then able to enter into unsecuredfinancing relationships with financing players whereby early paymentrequests from the vendors of the buyer, on approved invoices, aredirected to the financing player who funds the early payment request tothe vendor, using the credit line provided to the buyer. Simultaneouslythe UPM-enabled system can provide notification to the buyer that itsearly payment requests had been satisfied through a draw on its line ofcredit from the financing player. Further, the UPM-enabled system wouldallow the buyer to sync the transaction to its accounting platform,closing out the open payables to the vendor and creating a payable dueto the financing player in the amount of the invoice due to the vendor,less a portion of the fee that the financing player, through theUPM-enabled system, or directly with the buyer, agreed to share with thebuyer, due on the original date of the invoice from the vendor that wassatisfied in full. In so doing, in a nearly frictionless electronicprocess, financing players can participate in attractive yields whilebuyers uninterested in paying early can still provide that service totheir vendors, through financing players, and yet, experience noaccounting inefficiency while sharing in the financial benefit of theprogram. By way of example, if a vendor requested invoice 1 (alreadyapproved by the buyer), in the amount of $100 to be paid at a 3%discount, and the financing party had agreed to share 30% of the savingwith the buyer, the notification would be sent, through the UPM-enabledsystem, to the financing party, rather than the buyer. The financingparty could then send electronic check payment, through the UPM-enabledsystem, from the unsecured credit line provided for the benefit of thebuyer. In this example $97 would have been sent to the vendor insatisfaction of their invoice. In a near instant transaction the buyerwould be notified that invoice number 1 had been paid in full, from adraw from their unsecured credit line provided by the financing party,and the accounting entries could be synced to their accounting system.In this case, the accounting entry would be payment in full of a $100payable plus an amount due to financing party of $99, due on theidentical date invoice 1 was originally due (although extending termswould be available at the discretion of the buyer and financing party)with $1 being allocated to program savings (income) or otheridentifiable general ledger category of the buyer's choosing.

Another marketplace option is for the UPM-enabled system to provide theabove functionality directly, acting in a capacity as a financing party.Still, in another marketplace option, a buyer, who on its own may haveotherwise been unable to offer early payment of an invoice, in theircapacity as a vendor, through the UPM-enabled system, could dynamicallyevaluate the early payment offers from its buyers and deploy similaramounts to its vendors, for a stated spread. That is a company can beboth a buyer and a vendor. The company can request that vendors pay oneor more of the company's invoices early for a particular discount. Thecompany can use some or all of the proceeds to pay one or moreoutstanding invoices of its vendors. Said differently, the UPM-enabledsystem can enable a buyer (in its capacity as a vendor) to indicate thespread it would like to earn over the early payment requests availableto it from its customers, deploying similar early payment offers to itsvendors, for same spread. This can be done in an automatic fashion, justas the acceptance and payment of requests can be done in an automaticfashion.

Mobile Payments

As another example, the UPM-enabled system can enable mobile payments.For example, a user can have a mobile computing device that containsdata associated with the user's UPM account. This information can bepresented on the mobile computing device, for example, through a barcode or a QR code. A merchant can scan the presented account informationand send the account information along with an amount that is to be paidto the mobile device. The merchant can send the information in aninvoice or the UPM-enabled system can create an invoice from theinformation received from the merchant. This invoice can then beassociated with the user's UPM account. The user can then approve andauthorize payment of the invoice through the UPM-enabled system or ontheir mobile device connected to the UPM, or through their mobiledevice's app, which is connected to the UPM. For example, if a user wasin a retail store, at checkout upon completion of scanning the items tobe purchased the merchant could scan the bar code or QR Code on theuser's mobile device. Upon scanning, the merchant point of sale systemcan communicate the unique user identification to the UPM-enabledsystem, along with the final receipt amount, and the UPM can thenpresent the receipt on the user's mobile device. The user can then havethe option of tapping the approve and pay button. Tapping the approveand pay button can have the effect of communicating to the UPM-enabledsystem that the user had approved the purchase and had authorized anelectronic check in the amount of the receipt to the merchant,concluding the transaction. In another implementation, the merchantcould implement an affinity program through the UPM, applying savings atthe time of checkout, or alternatively, applying the transactionproceeds to an affinity account. The UPM can then, using processesdescribed above, deliver the electronic check to the account of themerchant, along with reconciling information back to the originalreceipt. In yet another implementation, for example when the user ispaying in a restaurant or a service provider, the user could see thereceipt on their phone and would have the option of adding a tip to thetotal bill. In yet another implementation, in the event the useridentified an error the user could reject the receipt and the merchantcould re-transmit a corrected receipt. In another implementation theuser could select the specific account they wanted to pay from, shouldthey choose to pay from an account other than their default account. Inyet another implementation the UPM-enabled system could provide, offeredthrough third parties, or directly, guarantee services, ensuring themerchant of cleared funds.

Peer-to-Peer Payments

The UPM-enabled system can also allow individuals to make/receivepayments from other individuals. A UPM user can request that a paymentbe made to any other UPM user. For example, a first user can use theUPM-enabled system to select a quantity of money to be transferred outof an account associated with the first user. The first user can thenrequest that the UPM-enabled system transfer the money to a second user.The first user, however, can identify the second user by name, UPMlogin, cell phone number, etc., without having to know the second user'sfinancial account information. Once the second user has been selected,the first user can authorize the UPM-enabled system, e.g., via selectinga pay button, to transfer the quantity of funds. The UPM-enabled systemcan then facilitate the transfer of the quantity of funds as describedabove in regard to UPM payments.

FIG. 9 is a block diagram of a computer system in accordance with anillustrative implementation. The computer system or computing device 900can be used to implement the UPM. The computing system 900 includes abus 905 or other communication component for communicating informationand a processor 910 or processing circuit coupled to the bus 905 forprocessing information. The computing system 900 can also include one ormore processors 910 or processing circuits coupled to the bus forprocessing information. The computing system 900 also includes mainmemory 915, such as a random access memory (RAM) or other dynamicstorage device, coupled to the bus 905 for storing information, andinstructions to be executed by the processor 910. Main memory 915 canalso be used for storing position information, temporary variables, orother intermediate information during execution of instructions by theprocessor 910. The computing system 900 may further include a read onlymemory (ROM) 910 or other static storage device coupled to the bus 905for storing static information and instructions for the processor 910. Astorage device 925, such as a solid state device, magnetic disk oroptical disk, is coupled to the bus 905 for persistently storinginformation and instructions.

The computing system 900 may be coupled via the bus 905 to a display935, such as a liquid crystal display, or active matrix display, fordisplaying information to a user. An input device 930, such as akeyboard including alphanumeric and other keys, may be coupled to thebus 905 for communicating information and command selections to theprocessor 910. In another implementation, the input device 930 has atouch screen display 935. The input device 930 can include a cursorcontrol, such as a mouse, a trackball, or cursor direction keys, forcommunicating direction information and command selections to theprocessor 910 and for controlling cursor movement on the display 935.

According to various implementations, the processes described herein canbe implemented by the computing system 900 in response to the processor910 executing an arrangement of instructions contained in main memory915. Such instructions can be read into main memory 915 from anothercomputer-readable medium, such as the storage device 925. Execution ofthe arrangement of instructions contained in main memory 915 causes thecomputing system 900 to perform the illustrative processes describedherein. One or more processors in a multi-processing arrangement mayalso be employed to execute the instructions contained in main memory915.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinventions or of what may be claimed, but rather as descriptions offeatures specific to particular implementations of particularinventions. Certain features described in this specification in thecontext of separate implementations can also be implemented incombination in a single implementation. Although features may bedescribed above as acting in certain combinations and even initiallyclaimed as such, one or more features from a claimed combination can insome cases be excised from the combination, and the claimed combinationmay be directed to a subcombination or variation of a subcombination. Inaddition, the actions recited in the claims and various describedimplementations may be performed in a different order and still achievedesirable results.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the implementations described above should not beunderstood as requiring such separation in all implementations, and itshould be understood that the described program components and systemscan generally be integrated in a single software product or packagedinto multiple software products.

1. A method comprising: receiving, at a universal payment computingdevice, a plurality of invoices associated with a vendor and one or morebuyers, wherein each invoice is associated with a respective buyer andcomprises an invoice amount to be paid by a deadline, wherein theuniversal payment computing device stores a second plurality of invoicesassociated with one or more vendors that are different than the vendor;sending each invoice to the respective buyer; determining, using aprocessor, possible early payment invoices that are available for earlypayment prior to the respective deadline from the plurality of invoices;sending notification to the vendor regarding the possible early paymentinvoices, wherein each notification includes a respective discount ofthe invoice; sending a request to one or more buyers associated with thepossible early payment invoices to make an early payment, wherein atleast one request includes a request for early payment of a partialinvoice amount; determining approval to receive early payment of one ormore of the possible early payment invoices; determining a vendorfinancial institution and a vendor account associated with the vendor;determining buyer financial institutions and buyer accounts associatedwith the one or more buyers, wherein the vendor is not required to knowthe buyer financial institutions and the buyer accounts; andfacilitating transfer of a quantity of funds from the buyer accounts atthe buyer financial institutions to the vendor account at the vendorfinancial institution, wherein the quantity of funds is based upon theinvoice amount in view of the respective discount of the one or more ofthe possible early payment invoices and includes the early payment ofthe partial invoice amount.
 2. The method of claim 1, whereindetermining approval comprises receiving approval from the vendor. 3.The method of claim 1, wherein determining approval comprises:determining the respective discount of one of the possible early paymentinvoices is acceptable to the vendor based upon a discount graphassociated with the vendor; and determining the respective discount isacceptable to the vendor.
 4. The method of claim 3, further comprisingdetermining the discount graph associated with the vendor based upon thebuyer associated with the one of the possible early payment invoices. 5.The method of claim 3, wherein determining the respective discount ofthe one request is acceptable comprises: determining an acceptablediscount rate based upon an age of the invoice associated with the oneof the possible early payment invoices; and determining the respectivediscount of the one of the possible early payment invoices is less thanor equal to the acceptable discount rate.
 6. (canceled)
 7. (canceled) 8.The method of claim 1, further comprising: calculating a prediction ofearly payment value for each of the possible early payment invoices; andordering the possible early payment invoices based upon the predictionof early payment values.
 9. The method of claim 8, further comprising:determining a first set of invoices to approve to receive payment basedupon the prediction of early payment value; and sending a request tomake early payment for each of the first set of invoices.
 10. The methodof claim 9, further comprising: calculating a total invoice amount basedupon the invoice amount and respective discount amount of each invoiceof the first set of invoices, wherein determining the first set ofinvoices is further based upon a sum of the total invoice amount for thefirst set of invoices being above a predetermined value.
 11. The methodof claim 10, further comprising determining a second set of invoices toapprove to receive early payment based upon the prediction of earlypayment values and not receiving early payment from one or more invoicesfrom the first set of invoices.
 12. A non-transitory computer-readablemedium having instructions stored thereon, the instructions comprising:instructions to receive, at a universal payment computing device, aplurality of invoices associated with a vendor and one or more buyers,wherein each invoice is associated with a respective buyer and comprisesan invoice amount to be paid by a deadline, wherein the universalpayment computing device stores a second plurality of invoicesassociated with one or more vendors that are different than the vendor;instructions to send each invoice to the respective buyer; instructionsto determine possible early payment invoices that are available forearly payment prior to the respective deadline from the plurality ofinvoices; instructions to send notification to the vendor regarding thepossible early payment invoices, wherein each notification includes arespective discount of the invoice; instructions to send a request toone or more buyers associated with the possible early payment invoicesto make an early payment, wherein at least one request includes arequest for early payment of a partial invoice amount; instructions todetermine approval to receive early payment of one or more of thepossible early payment invoices; instructions to determine a vendorfinancial institution and a vendor account associated with the vendor;instructions to determine buyer financial institutions and buyeraccounts associated with the one or more buyers, wherein the vendor isnot required to know the buyer financial institutions and the buyeraccounts; and instructions to facilitate transfer of a quantity of fundsfrom the buyer accounts at the buyer financial institutions to thevendor account at the vendor financial institution, wherein the quantityof funds is based upon the invoice amount in view of the respectivediscount of the one or more of the possible early payment invoices andincludes the early payment of the partial invoice amount.
 13. Thenon-transitory computer-readable medium of claim 12, wherein theinstructions to determine approval comprise instructions to receiveapproval from the vendor.
 14. The non-transitory computer-readablemedium of claim 12, wherein the instructions to determine approvalcomprise: instructions to determine the respective discount of one ofthe possible early payment invoices is acceptable to the vendor basedupon a discount graph associated with the vendor; and instructions todetermine the respective discount is acceptable to the vendor.
 15. Thenon-transitory computer-readable medium of claim 14, further comprisinginstructions to determine the discount graph associated with the vendorbased upon the buyer associated with the one of the possible earlypayment invoices.
 16. The non-transitory computer-readable medium ofclaim 14, wherein the instructions to determine the respective discountof one of the possible early payment invoices comprise: instructions todetermine an acceptable discount rate based upon an age of the invoiceassociated with the one of the possible early payment invoices; andinstructions to determine the respective discount of the one of thepossible early payment invoices is less than or equal to the acceptablediscount rate.
 17. (canceled)
 18. (canceled)
 19. The non-transitorycomputer-readable medium of claim 12, further comprising: instructionsto calculate a prediction of early payment value for each of thepossible early payment invoices; and instructions to order the possibleearly payment invoices based upon the prediction of early paymentvalues.
 20. A system comprising: one or more electronic processors of auniversal payment computing device configured to: receive a plurality ofinvoices associated with a vendor and one or more buyers, wherein eachinvoice is associated with a respective buyer and comprises an invoiceamount to be paid by a deadline, wherein the universal payment computingdevice stores a second plurality of invoices associated with one or morevendors that are different than the vendor; send each invoice to therespective buyer; determine possible early payment invoices that areavailable for early payment prior to the respective deadline from theplurality of invoices; send notification to the vendor regarding thepossible early payment invoices, wherein each notification includes arespective discount of the invoice; send a request to one or more buyersassociated with the possible early payment invoices to make an earlypayment, wherein at least one request includes a request for earlypayment of a partial invoice amount; determine approval to receive earlypayment of one or more of the possible early payment invoices; determinea vendor financial institution and a vendor account associated with thevendor; determine buyer financial institutions and buyer accountsassociated with the one or more buyers, wherein the vendor is notrequired to know the buyer financial institutions and the buyeraccounts; and facilitate transfer of a quantity of funds from the buyeraccounts at the buyer financial institutions to the vendor account atthe vendor financial institution, wherein the quantity of funds is basedupon the invoice amount in view of the respective discount of the one ormore of the possible early payment invoices and includes the earlypayment of the partial invoice amount.
 21. The system of claim 20,wherein the one or more electronic processors are further configured to:calculate a prediction of early payment value for each of the possibleearly payment invoices; and order the possible early payment invoicesbased upon the prediction of early payment values.
 22. The system ofclaim 21, wherein the one or more electronic processors are furtherconfigured to: determine a first set of invoices to approve to receivepayment based upon the prediction of early payment value; and send arequest to make early payment for each of the first set of invoices. 23.The system of claim 22, wherein the one or more electronic processorsare further configured to: calculate a total invoice amount based uponthe invoice amount and respective discount amount of each invoice of thefirst set of invoices, wherein determining the first set of invoices isfurther based upon a sum of the total invoice amount for the first setof invoices being above a predetermined value.
 24. The non-transitorycomputer-readable medium of claim 19, further comprising: instructionsto determine a first set of invoices to approve to receive payment basedupon the prediction of early payment value; and instructions to send arequest to make early payment for each of the first set of invoices.